Systems and methods for connecting merchant loyalty programs with payment cards

ABSTRACT

A computer-based method for providing a loyalty identifier to a merchant using a payment network is described. The method includes storing data including at least one loyalty identifier associated with a cardholder enrolled in a loyalty program and a corresponding payment card identifier, receiving a first authorization request message for a payment transaction initiated by a first cardholder using a first payment card at an originating merchant, the first authorization request message including a first merchant identifier and a first payment card identifier, determining a first loyalty program associated with the originating merchant based in part on the first merchant identifier and the data stored in the memory, determining a first loyalty identifier associated with the first cardholder for the first loyalty program based in part on the first payment card identifier and the data stored in the memory, and providing the first loyalty identifier to the originating merchant.

BACKGROUND OF THE DISCLOSURE

The field of the disclosure relates generally to merchant-based loyaltyprograms, and more particularly to determining a cardholder's loyaltyidentifier for a loyalty program based on the cardholder's payment card.

Many merchants offer loyalty programs, where the merchant monitors aconsumer's transactions with the merchant and then provides the consumerwith a reward based on those transactions. For example, a merchant mayprovide a coupon for $10 off goods and/or services after a customer haspurchased over $100 of goods and/or services from that merchant, or amerchant may provide the consumer with a coupon for a free coffee when aconsumer has conducted 10 transactions with the merchant. Many loyaltyprograms provide the consumer with a loyalty program membership cardwith a unique identifier. When the consumer makes a transaction with themerchant, the consumer shows his or her membership card and the uniqueidentifier is associated with the transaction. The transactionsassociated with the consumer's unique identifier are aggregated and whena threshold is reached the merchant may give the consumer a reward. Someloyalty programs count dollars spent, other programs count the number oftransactions or count points earned. Some other loyalty programs providea discount on the amount paid for every transaction.

Some of the loyalty programs provide the consumer with a personalizedmembership card. Other loyalty programs provide the consumer with amembership card with a unique identifier and then require the consumerto register the card with the merchant, usually online on the merchant'swebsite. To use these loyalty programs, the consumer must show the cardat each transaction. This can be problematic when the consumer hasloyalty program cards for multiple different merchants. In some loyaltyprograms, when the consumer doesn't have their card, the cashier may beable to look it up. However, this slows down the transaction process.

BRIEF DESCRIPTION OF THE DISCLOSURE

In one aspect, a computer-based method for providing a loyaltyidentifier to a merchant using a payment network is described. Themethod is implemented using a computing device in communication with amemory. The method includes storing data within the memory including (i)at least one loyalty identifier associated with a cardholder enrolled ina loyalty program and (ii) a corresponding payment card identifierassociated with the cardholder, and receiving a first authorizationrequest message for a payment transaction initiated by a firstcardholder using a first payment card at an originating merchant. Thefirst authorization request message includes a first merchant identifierand a first payment card identifier, where the first payment cardidentifier is associated with the first payment card issued by anissuing bank to the first cardholder. The method also determining by thecomputing device a first loyalty program associated with the originatingmerchant based in part on the first merchant identifier and the datastored in the memory, determining by the computing device a firstloyalty identifier associated with the first cardholder for the firstloyalty program based in part on the first payment card identifier andthe data stored in the memory, and providing the first loyaltyidentifier to the originating merchant.

In another aspect, a computing device for providing a loyalty identifierto a merchant using a payment network is described. The computing deviceincludes one or more processors communicatively coupled to one or morememory devices. The computing device is configured to store data withinthe one or more memory devices including (i) at least one loyaltyidentifier associated with a cardholder enrolled in a loyalty programand (ii) a corresponding payment card identifier associated with thecardholder, and receive a first authorization request message for apayment transaction initiated by a first cardholder using a firstpayment card at an originating merchant. The first authorization requestmessage including a first merchant identifier and a first payment cardidentifier, where the first payment card identifier is associated withthe first payment card issued by an issuing bank to the firstcardholder. The computing device is also configured to determine a firstloyalty program associated with the originating merchant based in parton the first merchant identifier and the data stored in the memory,determine a first loyalty identifier associated with the firstcardholder for the first loyalty program based in part on the firstpayment card identifier and the data stored in the memory, and providethe first loyalty identifier to the originating merchant

In a further aspect, a computer-readable storage medium havingcomputer-executable instructions embodied thereon is described. Whenexecuted by a computing device having at least one processor coupled toat least one memory device, the computer-executable instructions causethe processor to store data within the one or more memory devicesincluding (i) at least one loyalty identifier associated with acardholder enrolled in a loyalty program and (ii) a correspondingpayment card identifier associated with the cardholder, and receive afirst authorization request message for a payment transaction initiatedby a first cardholder using a first payment card at an originatingmerchant. The first authorization request message including a firstmerchant identifier and a first payment card identifier, where the firstpayment card identifier being associated with the first payment cardissued by an issuing bank to the first cardholder. Thecomputer-executable instructions also cause the processor to determine afirst loyalty program associated with the originating merchant based inpart on the first merchant identifier and the data stored in the memory,determine a first loyalty identifier associated with the firstcardholder for the first loyalty program based in part on the firstpayment card identifier and the data stored in the memory, and providethe first loyalty identifier to the originating merchant.

BRIEF DESCRIPTION OF THE DRAWINGS

FIGS. 1-8 show example embodiments of the methods and systems describedherein.

FIG. 1 is a schematic diagram illustrating an example multi-partytransaction card industry system for enabling ordinary payment-by-cardtransactions in which merchants and card issuers do not need to have aone-to-one special relationship.

FIG. 2 is a simplified block diagram of an example computer systemincluding a plurality of computer devices in accordance with one exampleembodiment of the present invention.

FIG. 3 illustrates an example configuration of a client system shown inFIG. 2, in accordance with one embodiment of the present disclosure.

FIG. 4 illustrates an example configuration of the server system shownin FIG. 2, in accordance with one embodiment of the present disclosure.

FIG. 5 is a schematic diagram which illustrates an example ofintegrating a multi-party payment card system with determiningcardholder loyalty identifiers for loyalty programs.

FIG. 6 is a flowchart illustrating an example of the process ofdetermining a loyalty identifier for a cardholder based on anauthorization request using the system shown in FIG. 2, in accordancewith one embodiment of the disclosure.

FIG. 7 is a flowchart illustrating an example process of a cardholderregistering for a loyalty program using the system shown in FIG. 2, inaccordance with one embodiment of the present disclosure.

FIG. 8 is a diagram of components of one or more example computingdevices that may be used in the system shown in FIG. 2.

DETAILED DESCRIPTION OF THE DISCLOSURE

The following detailed description describes embodiments of thedisclosure by way of example and not by way of limitation. Thedescription clearly enables one skilled in the art to make and use theembodiments of the disclosure. The description describes severalembodiments, adaptations, variations, alternatives, and uses of thedisclosure, including what is presently believed to be the best mode ofcarrying out the disclosure. The disclosure is described as applied toan example embodiment, namely, methods and systems for determining acardholder's loyalty identifier for a loyalty program based on thecardholder's payment card. More specifically, the disclosure describes aloyalty program (“LP”) computing device configured to receive anauthorization request message for a payment transaction originating froma merchant for a cardholder, determine the cardholder's loyaltyidentifier for a loyalty program associated with the merchant, andtransmit the determined loyalty identifier to the merchant for furtheruse by the merchant.

The purpose of tying the cardholder's payment card with the cardholder'sloyalty programs is to provide the cardholder with the convenience ofnot having to carry multiple cards for multiple loyalty programs. Whenthe cardholder uses their regular payment card to pay for a transactionwith a merchant, the LP computing device determines if the cardholder isa member of that merchant's loyalty program. If the cardholder is amember, then the LP computing device transmits the cardholder's loyaltyidentifier to that merchant so that the transaction is associated withthe cardholder's loyalty program account.

In the example embodiment, the LP computing device is configured for usewith a payment card processing network such as, for example, aninterchange network. The LP computing device includes a memory deviceand a processor in communication with the memory device and isprogrammed to communicate with the payment network (also known as thepayment processor) to receive authorization request messages for paymenttransactions originating from a merchant for a cardholder. The paymentnetwork is configured to process payment card transactions between themerchant and its acquirer bank, and the cardholder and their issuerbank. Authorization request messages include merchant identifiers andcardholder identifiers.

In the example embodiment, the LP computing device stores in a databasea collection of loyalty programs which contain loyalty identifiers forthe members of the loyalty programs. When the payment network receivesan authorization request for a cardholder transaction from a merchant,the LP computing device determines if the cardholder has a loyaltyidentifier for the merchant's loyalty program. If the cardholder has anassociated loyalty identifier, then the LP computing device transmitsthe cardholder's loyalty identifier to the payment card processingnetwork, which transmits the cardholder's loyalty identifier to themerchant in the transaction authorization response message along with anauthorization code for the transaction.

In the above embodiment, each loyalty program is associated with amerchant, who provides rewards to consumers based on the consumer'spurchases from the merchant. Each loyalty program requires consumers toregister for the loyalty program and issues a unique loyalty identifierto each registered consumer. The LP computing device associates apayment cardholder with a loyalty program by storing in the database thecardholder's loyalty program identifier and associating the loyaltyidentifier with the cardholder's payment card account number.

When a payment transaction is processed by the payment network, the LPcomputing device receives a merchant identifier for the originatingmerchant and automatically generates a query that queries the databaseto determine if the originating merchant associated with the paymenttransaction is associated with one of the stored loyalty programs. Ifthe originating merchant has an associated loyalty program, the LPcomputing device queries the database to retrieve the loyalty identifierof the cardholder associated with the payment transaction. In someembodiments, the LP computing device transmits the retrieved loyaltyidentifier to the payment network, which transmits the cardholder'sloyalty identifier to the merchant with the transaction authorizationresponse message. In other embodiments, LP computing device stores theloyalty identifiers from the processed payment transactions andperiodically transmits the stored loyalty identifiers associated withtransactions to the merchant in batches.

The payment network may facilitate a payment cardholder registering thepayment cardholder's loyalty identifier for a loyalty program in aloyalty tracking service. In some embodiments, the LP computing devicefacilitates the cardholder typing his or her loyalty identifier into thedatabase. In other embodiments, the LP computing device may store thecardholder's loyalty identifier by receiving from the cardholder apicture of his or her loyalty program card and determining the loyaltyidentifier from that picture.

In some further embodiments, the loyalty program may be configured toprovide a reward to a registered cardholder based on the number ofdollars spent, number of points earned, or number of transactions. Inother embodiments, the loyalty program may be configured to provide thecardholder with a discount on products or services purchased. In thisparticular embodiment, the LP computing device may recalculate thetransaction and reinitiate the payment transaction approval process forthe new amount.

The methods and systems described herein may be implemented usingcomputer programming or engineering techniques including computersoftware, firmware, hardware, or any combination or subset wherein atechnical effect of the systems and processes described herein isachieved by performing at least one of the following steps: (a)receiving a loyalty identifier for a cardholder by (1) receiving apicture of a merchant-based loyalty program card associated with thecardholder and (2) determining the loyalty identifier associated withthe cardholder based on the picture; (b) storing at least one loyaltyidentifier for a merchant-based loyalty program in association with acardholder's payment card identifier, wherein the merchant-based loyaltyprogram provides rewards based on at least one of number of pointsearned, number of dollars spent, and number of transactions completed;(c) receiving a first authorization request message for a paymenttransaction originating from an originating merchant for a cardholder,the first authorization request message includes a merchant identifierand the cardholder's payment card identifier associated with a paymentcard, where the payment transaction was initiated by the cardholderusing a payment card issued by an issuing bank; (d) determining amerchant-based loyalty program associated with the originating merchantbased in part on the merchant identifier; (e) determining the loyaltyidentifier associated with the cardholder for the merchant-based loyaltyprogram based in part on the cardholder identifier; (f) transmitting thedetermined loyalty identifier to a payment processing network to beincluded in a transaction authorization response sent to the merchant.

As used herein, the terms “transaction card,” “financial transactioncard,” and “payment card” refer to any suitable transaction card, suchas a credit card, a debit card, a prepaid card, a charge card, amembership card, a promotional card, a frequent flyer card, anidentification card, a prepaid card, a gift card, and/or any otherdevice that may hold payment account information, such as mobile phones,Smartphones, personal digital assistants (PDAs), key fobs, and/orcomputers. Each type of transactions card can be used as a method ofpayment for performing a transaction.

In one embodiment, a computer program is provided, and the program isembodied on a computer readable medium. In an example embodiment, thesystem is executed on a single computer system, without requiring aconnection to a server computer. In a further example embodiment, thesystem is being run in a Windows® environment (Windows is a registeredtrademark of Microsoft Corporation, Redmond, Wash.). In yet anotherembodiment, the system is run on a mainframe environment and a UNIX®server environment (UNIX is a registered trademark of X/Open CompanyLimited located in Reading, Berkshire, United Kingdom). The applicationis flexible and designed to run in various different environmentswithout compromising any major functionality. In some embodiments, thesystem includes multiple components distributed among a plurality ofcomputing devices. One or more components are in the form ofcomputer-executable instructions embodied in a computer-readable medium.The systems and processes are not limited to the specific embodimentsdescribed herein. In addition, components of each system and eachprocess can be practiced independently and separately from othercomponents and processes described herein. Each component and processcan also be used in combination with other assembly packages andprocesses.

In one embodiment, a computer program is provided, and the program isembodied on a computer readable medium and utilizes a Structured QueryLanguage (SQL) with a client user interface front-end for administrationand a web interface for standard user input and reports. In anotherembodiment, the system is web enabled and is run on a business-entityintranet. In yet another embodiment, the system is fully accessed byindividuals having an authorized access outside the firewall of thebusiness-entity through the Internet. In a further embodiment, thesystem is being run in a Windows® environment (Windows is a registeredtrademark of Microsoft Corporation, Redmond, Wash.). The application isflexible and designed to run in various different environments withoutcompromising any major functionality.

As used herein, an element or step recited in the singular and precededwith the word “a” or “an” should be understood as not excluding pluralelements or steps, unless such exclusion is explicitly recited.Furthermore, references to “example embodiment” or “one embodiment” ofthe present disclosure are not intended to be interpreted as excludingthe existence of additional embodiments that also incorporate therecited features.

As used herein, the term “database” may refer to either a body of data,a relational database management system (RDBMS), or to both. A databasemay include any collection of data including hierarchical databases,relational databases, flat file databases, object-relational databases,object oriented databases, and any other structured collection ofrecords or data that is stored in a computer system. The above examplesare for example only, and thus are not intended to limit in any way thedefinition and/or meaning of the term database. Examples of RDBMS'sinclude, but are not limited to including, Oracle® Database, MySQL, IBM®DB2, Microsoft® SQL Server, Sybase®, and PostgreSQL. However, anydatabase may be used that enables the systems and methods describedherein. (Oracle is a registered trademark of Oracle Corporation, RedwoodShores, Calif.; IBM is a registered trademark of International BusinessMachines Corporation, Armonk, N.Y.; Microsoft is a registered trademarkof Microsoft Corporation, Redmond, Wash.; and Sybase is a registeredtrademark of Sybase, Dublin, Calif.)

The term processor, as used herein, may refer to central processingunits, microprocessors, microcontrollers, reduced instruction setcircuits (RISC), application specific integrated circuits (ASIC), logiccircuits, and any other circuit or processor capable of executing thefunctions described herein.

As used herein, the terms “software” and “firmware” are interchangeable,and include any computer program stored in memory for execution by aprocessor, including RAM memory, ROM memory, EPROM memory, EEPROMmemory, and non-volatile RAM (NVRAM) memory. The above memory types arefor example only, and are thus not limiting as to the types of memoryusable for storage of a computer program.

The term loyalty program, as used herein, may refer to a loyalty programassociated with payment cards, hotel stays, airline flights, carrentals, websites visited, gaming, and any other item capable ofgenerating rewards. The examples are not limiting as to the items that aloyalty program may be associated with. A loyalty program may be withparticular merchant, a loyalty program may cover a partnership betweenmultiple merchants, or a loyalty programs may cover partnerships betweenmerchants, issuing banks, and/or a payment processing network, or anycombination thereof.

FIG. 1 is a schematic diagram illustrating an example multi-partytransaction card industry system 120 for enabling ordinarypayment-by-card transactions in which merchants 124 and card issuers 130do not need to have a one-to-one special relationship. Embodimentsdescribed herein may relate to a transaction card system, such as acredit card payment system using the MasterCard® interchange network.The MasterCard® interchange network is a set of proprietarycommunications standards promulgated by MasterCard InternationalIncorporated® for the exchange of financial transaction data and thesettlement of funds between financial institutions that are members ofMasterCard International Incorporated®. (MasterCard is a registeredtrademark of MasterCard International Incorporated located in Purchase,N.Y.).

In a typical transaction card system, a financial institution called the“issuer” issues a transaction card, such as a credit card, to a consumeror cardholder 122, who uses the transaction card to tender payment for apurchase from a merchant 124. To accept payment with the transactioncard, merchant 124 must normally establish an account with a financialinstitution that is part of the financial payment system. This financialinstitution is usually called the “merchant bank,” the “acquiring bank,”or the “acquirer.” When cardholder 122 tenders payment for a purchasewith a transaction card, merchant 124 requests authorization from amerchant bank 126 for the amount of the purchase. The request may beperformed over the telephone, but is usually performed through the useof a point-of-sale terminal, which reads cardholder's 122 accountinformation from a magnetic stripe, a chip, or embossed characters onthe transaction card and communicates electronically with thetransaction processing computers of merchant bank 126. Alternatively,merchant bank 126 may authorize a third party to perform transactionprocessing on its behalf. In this case, the point-of-sale terminal willbe configured to communicate with the third party. Such a third party isusually called a “merchant processor,” an “acquiring processor,” or a“third party processor.”

Using an interchange network 128, computers of merchant bank 126 ormerchant processor will communicate with the computers of an issuer bank130 to determine whether cardholder's 122 account 132 is in goodstanding and whether the purchase is covered by cardholder's 122available credit line. Based on these determinations, the request forauthorization will be declined or accepted. If the request is accepted,an authorization code is issued to merchant 124.

When a request for authorization is accepted, the available credit lineof cardholder's 122 account 132 is decreased. Normally, a charge for apayment card transaction is not posted immediately to cardholder's 122account 132 because bankcard associations, such as MasterCardInternational Incorporated®, have promulgated rules that do not allowmerchant 124 to charge, or “capture,” a transaction until goods areshipped or services are delivered. However, with respect to at leastsome debit card transactions, a charge may be posted at the time of thetransaction. When merchant 124 ships or delivers the goods or services,merchant 124 captures the transaction by, for example, appropriate dataentry procedures on the point-of-sale terminal. This may includebundling of approved transactions daily for standard retail purchases.If cardholder 122 cancels a transaction before it is captured, a “void”is generated. If cardholder 122 returns goods after the transaction hasbeen captured, a “credit” is generated. Interchange network 128 and/orissuer bank 130 stores the transaction card information, such as amerchant identifier, a cardholder identifier, and a transaction amount,in a database 220 (shown in FIG. 2).

After a purchase has been made, a clearing process occurs to transferadditional transaction data related to the purchase among the parties tothe transaction, such as merchant bank 126, interchange network 128, andissuer bank 130. More specifically, during and/or after the clearingprocess, additional data, such as a time of purchase, a merchant name, atype of merchant, purchase information, cardholder account information,a type of transaction, itinerary information, information regarding thepurchased item and/or service, and/or other suitable information, isassociated with a transaction and transmitted between parties to thetransaction as transaction data, and may be stored by any of the partiesto the transaction. In the exemplary embodiment, when cardholder 122purchases travel, such as airfare, a hotel stay, and/or a rental car, atleast partial itinerary information is transmitted during the clearanceprocess as transaction data. When interchange network 128 receives theitinerary information, interchange network 128 routes the itineraryinformation to database 220.

For debit card transactions, when a request for a personalidentification number (PIN) authorization is approved by the issuer,cardholder's account 132 is decreased. Normally, a charge is postedimmediately to cardholder's account 132. The payment card associationthen transmits the approval to the acquiring processor for distributionof goods/services or information, or cash in the case of an automatedteller machine (ATM).

After a transaction is authorized and cleared, the transaction issettled among merchant 124, merchant bank 126, and issuer bank 130.Settlement refers to the transfer of financial data or funds amongmerchant's 124 account, merchant bank 126, and issuer bank 130 relatedto the transaction. Usually, transactions are captured and accumulatedinto a “batch,” which is settled as a group. More specifically, atransaction is typically settled between issuer bank 130 and interchangenetwork 128, and then between interchange network 128 and merchant bank126, and then between merchant bank 126 and merchant 124.

FIG. 2 is a simplified block diagram of an example system 200 includinga plurality of computer devices in accordance with one exampleembodiment of the present invention. In the example embodiment, system200 may be used for performing payment-by-card transactions received aspart of processing cardholder transactions. In addition, system 200 is apayment processing system that includes a loyalty program (“LP”)computing device 224 configured to determine a cardholder's loyaltyidentifier based on an authorization request message. As described belowin more detail, LP computing device 224 is configured to receive anauthorization request message for a payment transaction originating froma merchant 124 for a cardholder 122 (both shown in FIG. 1), determinethe cardholder's loyalty identifier for the merchant's loyalty program,and transmit the determined loyalty identifier.

In the example embodiment, client systems 214 are computers that includea web browser or a software application, which enables client systems214 to access server system 212 using the Internet. More specifically,client systems 214 are communicatively coupled to the Internet throughmany interfaces including, but not limited to, at least one of anetwork, such as the Internet, a local area network (LAN), a wide areanetwork (WAN), or an integrated services digital network (ISDN), adial-up-connection, a digital subscriber line (DSL), a cellular phoneconnection, and a cable modem. Client systems 214 can be any devicecapable of accessing the Internet including, but not limited to, adesktop computer, a laptop computer, a personal digital assistant (PDA),a cellular phone, a smartphone, a tablet, a phablet, or other web-basedconnectable equipment.

A database server 216 is communicatively coupled to a database 220 thatstores data. In one embodiment, database 220 includes loyalty programinformation including at least one merchant identifier and loyaltyidentifiers. In the example embodiment, database 220 is stored remotelyfrom server system 212. In some embodiments, database 220 isdecentralized. In the example embodiment, a person can access database220 via client systems 214 by logging onto server system 212, asdescribed herein.

The LP computing device 224 is communicatively coupled with the serversystem 212. The LP computing device 224 can access the server system 212to store and access data and to communicate with the client systems 214through the server system 212. In some embodiments, the LP computingdevice 224 may be associated with, or is part of the payment system, orin communication with the payment card system payment network 120, shownin FIG. 1. In other embodiments, the PG computing device 224 isassociated with a third party and is merely in communication with thepayment network 120.

One or more point of sale systems 222 are communicatively coupled withthe server system 212. The one or more point of sale systems 222 can bemerchants 124 shown in FIG. 1, where the point of sale systems 222 arecommunicatively coupled with the server system through the paymentnetwork 120. Point of sale systems 222 may be, but are not limited to,machines that accept card swipes, online payment portals, or storedpayment card numbers for recurring transactions.

In some embodiments, server system 212 may be associated with afinancial transaction interchange network 128 shown in FIG. 1, and maybe referred to as an interchange computer system. Server system 212 maybe used for processing transaction data and for registering cardholdersand/or merchants into a plurality of programs offered by the interchangenetwork, including, but not limited to, a rewards program. In addition,at least one of client systems 214 may include a computer systemassociated with an issuer of a transaction card. Accordingly, serversystem 212 and client systems 214 may be utilized to process transactiondata relating to purchases a cardholder 122 makes utilizing atransaction card processed by the interchange network and issued by theassociated issuer. At least one client system 214 may be associated witha user or a cardholder 122 seeking to register, access information, orprocess a transaction with at least one of the interchange network 128,the issuer 130, or the merchant 124. In addition, client systems 214 orpoint of sales devices 222 may include point-of-sale (POS) devicesassociated with a merchant 124 and used for processing paymenttransactions. POS devices 222 may be, but are not limited to, machinesthat accept card swipes, online payment portals, or stored payment cardnumbers for recurring transactions.

In some embodiments, instead of reading a magnetic strip on a card,biometric data may be used to verify a cardholder's payment card accountinformation. For example, the POS device 222 may scan the cardholder'sfingerprint, handprint, retina, iris, or any other biometric featureused for identifying a person. This scan would then be provided to thepayment network. This scan may be provided to the payment network 120through the authorization request message.

FIG. 3 illustrates an example configuration of a client system 214 shownin FIG. 2, in accordance with one embodiment of the present disclosure.User computer device 302 is operated by a user 301. User computer device302 may include, but is not limited to, client systems 214 (shown inFIG. 2). User computer device 302 includes one or more processors 305for executing instructions. In some embodiments, executable instructionsare stored in to one or more memory areas 310. Processor 305 may includeone or more processing units (e.g., in a multi-core configuration).Memory area 310 is any device allowing information such as executableinstructions and/or transaction data to be stored and retrieved. Memoryarea 310 may include one or more computer readable media.

User computer device 302 also includes at least one media outputcomponent 315 for presenting information to user 301. Media outputcomponent 315 is any component capable of conveying information to user301. In some embodiments, media output component 315 includes an outputadapter (not shown) such as a video adapter and/or an audio adapter. Anoutput adapter is operatively coupled to processor 305 and operativelycoupleable to an output device such as a display device (e.g., a cathoderay tube (CRT), liquid crystal display (LCD), light emitting diode (LED)display, or “electronic ink” display) or an audio output device (e.g., aspeaker or headphones). In some embodiments, media output component 315is configured to present a graphical user interface (e.g., a web browserand/or a client application) to user 301. A graphical user interface mayinclude, for example, an online store interface for viewing and/orpurchasing items, and/or a wallet application for managing paymentinformation. In some embodiments, user computer device 302 includes aninput device 320 for receiving input from user 301. User 301 may useinput device 320 to, without limitation, select and/or enter one or moreitems to purchase and/or a purchase request, or to access credentialinformation, and/or payment information. Input device 320 may include,for example, a keyboard, a pointing device, a mouse, a stylus, a touchsensitive panel (e.g., a touch pad or a touch screen), a gyroscope, anaccelerometer, a position detector, a biometric input device, and/or anaudio input device. A single component such as a touch screen mayfunction as both an output device of media output component 315 andinput device 320.

User computer device 302 may also include a communication interface 325,communicatively coupled to a remote device such as server system 212(shown in FIG. 2). Communication interface 325 may include, for example,a wired or wireless network adapter and/or a wireless data transceiverfor use with a mobile telecommunications network.

Stored in memory area 310 are, for example, computer readableinstructions for providing a user interface to user 301 via media outputcomponent 315 and, optionally, receiving and processing input from inputdevice 320. A user interface may include, among other possibilities, aweb browser and/or a client application. Web browsers enable users, suchas user 301, to display and interact with media and other informationtypically embedded on a web page or a website from server system 212. Aclient application allows user 301 to interact with, for example, serversystem 212. For example, instructions may be stored by a cloud service,and the output of the execution of the instructions sent to the mediaoutput component 315.

FIG. 4 illustrates an example configuration of the server system 212shown in FIG. 2, in accordance with one embodiment of the presentdisclosure. Server computer device 401 may include, but is not limitedto, database server 216 (shown in FIG. 2). Server computer device 401also includes one or more processors 405 for executing instructions.Instructions may be stored in one or more memory areas 410. Processor405 may include one or more processing units (e.g., in a multi-coreconfiguration).

Processor 405 is operatively coupled to a communication interface 415such that server computer device 401 is capable of communicating with aremote device such as another server computer device 401, client systems214, or LP computing device 224 (both shown in FIG. 2). For example,communication interface 415 may receive requests from client systems 214via the Internet, as illustrated in FIG. 2.

Processor 405 may also be operatively coupled to a storage device 434.Storage device 434 is any computer-operated hardware suitable forstoring and/or retrieving data, such as, but not limited to, dataassociated with database 220 (shown in FIG. 2). In some embodiments,storage device 434 is integrated in server computer device 401. Forexample, server computer device 401 may include one or more hard diskdrives as storage device 434. In other embodiments, storage device 434is external to server computer device 401 and may be accessed by aplurality of server computer devices 401. For example, storage device434 may include a storage area network (SAN), a network attached storage(NAS) system, and/or multiple storage units such as hard disks and/orsolid state disks in a redundant array of inexpensive disks (RAID)configuration.

In some embodiments, processor 405 is operatively coupled to storagedevice 434 via a storage interface 420. Storage interface 420 is anycomponent capable of providing processor 405 with access to storagedevice 434. Storage interface 420 may include, for example, an AdvancedTechnology Attachment (ATA) adapter, a Serial ATA (SATA) adapter, aSmall Computer System Interface (SCSI) adapter, a RAID controller, a SANadapter, a network adapter, and/or any component providing processor 405with access to storage device 434.

Processor 405 executes computer-executable instructions for implementingaspects of the disclosure. In some embodiments, the processor 405 istransformed into a special purpose microprocessor by executingcomputer-executable instructions or by otherwise being programmed. Forexample, the processor 405 is programmed with instructions such asillustrated in FIGS. 6 & 7.

FIG. 5 is a schematic diagram 500 which illustrates an example ofintegrating a multi-party payment card system 120 (shown in FIG. 1) withdetermining cardholder loyalty identifiers for loyalty programs. In theexample embodiment, when a cardholder 122 initiates a purchase 510 at anoriginating merchant 124 with a payment card, an authorization request520 is sent to the acquirer 126, to the payment network 128, and then tothe issuer processor 130, as shown in FIG. 1. The cardholder's purchase510 may be initiated through many methods including, but not limited to,a card swipe, an online purchase, or a recurring charge and may beinitiate by one of the point-of-sale devices 222, shown in FIG. 2. Theauthorization request 520 includes transaction information including amerchant identifier, a cardholder identifier associated with the paymentcard, and other data. In the example embodiment, the LP computing device224 is associated with the payment network 128 and thus the databaseaccessed by the LP computing device 224 is a payment processor database.In another embodiment, the LP computing device 224 may be separate fromthe payment network 128 and thus the database accessed by the LPcomputing device 224 is an LP database.

The LP computing device 224 stores in the database 220 (show in FIG. 2)a plurality of loyalty programs, where each loyalty program may containat least one merchant identifier and a plurality of loyalty identifiers,and where each loyalty identifier is associated with a cardholderidentifier. In the example embodiment, the cardholder identifier is thecardholder's payment card account number. The LP computing device 224uses the merchant identifier from the authorization request 520 to querythe database 220 to determine which, if any, loyalty program isassociated with the originating merchant 124. If an appropriate loyaltyprogram is found, then the LP computing device 224 uses the cardholderidentifier to query the database 220 to retrieve the loyalty identifierassociated with the cardholder 122. While in this embodiment, the LPcomputing device 224 queries the database 220 twice, in otherembodiments determining the loyalty program and determining the loyaltyidentifier for the cardholder 122 could be accomplished in one query.

In the example embodiment, the LP computing device 224 transmits theretrieved loyalty identifier 530 to the payment network 128. The paymentnetwork formats loyalty identifier 530 so that is can be included withina transaction authorization response 540 and transmits the retrievedloyalty identifier 530 to the merchant 124 with the transactionauthorization response 540. In other embodiments, the LP computingdevice 224 stores the retrieved loyalty identifiers 530 from theprocessed payment transactions and periodically transmits the storedloyalty identifiers associated with transactions to the merchant 124 inbatches.

In the example embodiment, the LP computing device 224 enables amerchant 124 to register a loyalty program. In this embodiment, LPcomputing device 224 can receive from the merchant 124 loyalty programregistration information 550. The loyalty program registrationinformation 550 may include one or more merchant identifiers associatedwith the loyalty program, one or more formats for loyalty identifiersfor that loyalty program, and other information to identify the loyaltyprogram and associated loyalty identifiers.

In the example embodiment, the LP computing device 224 enablescardholders 122 to register with a loyalty program. In this embodiment,the LP computing device 224 receives a cardholder's loyalty identifier560 and associates the loyalty identifier 560 with the cardholderidentifier and the associated loyalty program.

In the example embodiments, the loyalty program may be configured toprovide a reward to a registered cardholder 122 based on the number ofdollars spent, number of points earned, or number of transactions. Inother embodiments, the loyalty program may be configured to provide thecardholder 122 with a discount on products or services purchased. Insuch embodiments, the authorization request 520 also includes atransaction amount. When the LP computing device 224 determines theloyalty program, the LP computing device 224 also determines a discountfor the transaction. The LP computing device 224 recalculates thetransaction amount and reinitiates the payment transaction approvalprocess for the discounted amount. In other embodiments, the differencebetween the original transaction amount and the discounted amount couldbe provided to the cardholder 122 as a refund or rebate.

FIG. 6 is a flowchart illustrating an example of the process 600 ofdetermining a loyalty identifier for a cardholder 122 (shown in FIG. 1)based on an authorization request 520 (shown in FIG. 5) using the system200 shown in FIG. 2, in accordance with one embodiment of thedisclosure. Process 600 may be implemented by a computing device, forexample the LP computing device 224 (shown in FIG. 2). In the exampleembodiment, the LP computing device 224 receives 610 the authorizationrequest 520. The LP computing device 224 determines 620 a merchantidentifier and a cardholder identifier associated with a payment cardfrom the authorization request 520. The LP computing device 224determines 630 a loyalty program associated with that merchantidentifier. The LP computing device 224 uses the merchant identifierfrom the authorization request 520 to query the database 220 (shown inFIG. 2) to determine which, if any, loyalty program is associated withthe originating merchant 124 (shown in FIG. 1). If an appropriateloyalty program is found, then the LP computing device 224 determines640 a loyalty identifier associated with the cardholder identifier forthe determined loyalty program. The LP computing device 224 uses thecardholder identifier to query the database 220 to retrieve the loyaltyidentifier associated with the cardholder 122. While in this embodiment,the LP computing device 224 queries the database 220 twice, in steps 630and 640, in other embodiments these steps could be combined into onequery. The LP computing device 224 transmits 650 the determined loyaltyidentifier to the originating merchant 124.

FIG. 7 is a flowchart illustrating an example process 700 of acardholder 122 (shown in FIG. 1) registering for a loyalty program usingthe system 200 shown in FIG. 2, in accordance with one embodiment of thepresent disclosure. Process 700 may be implemented using a computingdevice, for example the LP computing device 224 (shown in FIG. 2). Thepayment network 120 (shown in FIG. 1) may facilitate a paymentcardholder registering the payment cardholder's loyalty identifier for aloyalty program in a loyalty tracking service. In the exampleembodiment, the LP computing device 224 receives 710 a request from acardholder 122 (shown in FIG. 1) to register a loyalty identifierassociated with a loyalty program. The LP computing device 224 mayreceive the request from the cardholder 122 through communication withclient system 214 via server system 212 (both shown in FIG. 2). The LPcomputing device 224 receives 720 a cardholder identifier associatedwith a payment card issued by an issuing bank 130 (shown in FIG. 1) forthe cardholder 122. In some embodiments, the cardholder identifier maythe cardholder's payment card account number. The LP computing device224 instructs client system 214 to display 730 the available loyaltyprograms, which may be loyalty programs that have provided loyaltyprogram registration information 550 as shown in FIG. 5. The LPcomputing device 224 instructs the cardholder's client system 214 (shownin FIG. 2) to display to the cardholder 122 the available loyaltyprograms so that the cardholder 122 may select a loyalty program. Next,the LP computing device 224 receives 740 the cardholder's selection ofwhich loyalty program the cardholder 122 is registering for from thecardholder's client system 214.

In the example embodiment, the LP computing device 224 receives 750 apicture of the cardholder's loyalty program membership card. The LPcomputing device 224 determines 760 the cardholder's loyalty identifierbased on the picture. In some embodiments, this determination may beaccomplished by the LP computing device 224 reading the loyaltyidentifier off of the loyalty program membership card, for example usingoptical character recognition (OCR) or the like. In other embodiments,this determination may be accomplished by the LP computing device 224reading a bar code, or similar machine readable code, on the card anddetermining the loyalty identifier from the bar code. Then the LPcomputing device 224 stores 770 the determined loyalty identifier forthe selected loyalty program and associates the determined loyaltyidentifier with the cardholder identifier. In the example embodiment,the LP computing device 224 stores the determined loyalty identifier inthe database 220 (shown in FIG. 2), where the database 220 contains theselected loyalty program. In other embodiments, instead of receiving apicture of the cardholder's loyalty program membership card, the LPcomputing device 224 may receive the loyalty identifier directly by thecardholder 122 submitting the loyalty identifier, for example by typingthe identifier.

In some embodiments, instead of reading a magnetic strip on a loyaltyprogram membership card or receiving data wirelessly from a fob device,a cardholder's identity may be authenticated by biometric data of thecardholder. In these embodiments, LP computing device 224 may retrievethe cardholder's loyalty identifier from a consumer profile stored in acloud device (not shown). The cardholder identifier received by the LPcomputing device 224 may be a biometric identifier of the cardholder122, such as data from a scan of the cardholder's fingerprint,handprint, retina, iris, or any other biometric feature used foridentifying a person. The LP computing device 224 would query thedatabase 220 with the biometric identifier when determining 640 aloyalty identifier associated with the cardholder identifier for thedetermined loyalty program, as shown in FIG. 6.

FIG. 8 is a diagram 800 of components of one or more example computingdevices that may be used in the system 200 shown in FIG. 2. In someembodiments, computing device 810 is similar to server system 212; itmay also be similar to LP computing device 224 (both shown in FIG. 5).Database 820 may be coupled with several separate components withincomputing device 810, which perform specific tasks. In this embodiment,database 820 stores loyalty programs 822, merchant identifiers 824,cardholder identifiers 826, and loyalty identifiers 828.

Computing device 810 includes the database 820, as well as data storagedevices 830. Computing device 810 also includes a communicationcomponent 840 for receiving an authorization request 520 (shown in FIG.5) and transmitting a retrieved loyalty identifier 530 (shown in FIG.3). Communication component 840 may include, for example, a wired orwireless network adapter and/or a wireless data transceiver for use witha mobile telecommunications network. Computing device 810 also includesa determining component 850 for determining a loyalty program 822 basedon a merchant identifier 824 and determining a loyalty identifier 828based on a cardholder identifier 826. A processing component 860 assistswith execution of computer-executable instructions associated with thesystem.

The systems and processes are not limited to the specific embodimentsdescribed herein. In addition, components of each system and eachprocess can be practiced independent and separate from other componentsand processes described herein. Each component and process also can beused in combination with other assembly packages and processes.

Having described aspects of the disclosure in detail, it will beapparent that modifications and variations are possible withoutdeparting from the scope of aspects of the disclosure as defined in theappended claims. As various changes could be made in the aboveconstructions, products, and methods without departing from the scope ofaspects of the disclosure, it is intended that all matter contained inthe above description and shown in the accompanying drawings shall beinterpreted as illustrative and not in a limiting sense.

While the disclosure has been described in terms of various specificembodiments, those skilled in the art will recognize that the disclosurecan be practiced with modification within the spirit and scope of theclaims.

As will be appreciated based on the foregoing specification, theabove-described embodiments of the disclosure may be implemented usingcomputer programming or engineering techniques including computersoftware, firmware, hardware or any combination or subset thereof. Anysuch resulting program, having computer-readable code means, may beembodied or provided within one or more computer-readable media, therebymaking a computer program product, i.e., an article of manufacture,according to the discussed embodiments of the disclosure. Examplecomputer-readable media may be, but are not limited to, a flash memorydrive, digital versatile disc (DVD), compact disc (CD), fixed (hard)drive, diskette, optical disk, magnetic tape, semiconductor memory suchas read-only memory (ROM), and/or any transmitting/receiving medium suchas the Internet or other communication network or link. By way ofexample and not limitation, computer-readable media comprisecomputer-readable storage media and communication media.Computer-readable storage media are tangible and non-transitory andstore information such as computer-readable instructions, datastructures, program modules, and other data. Communication media, incontrast, typically embody computer-readable instructions, datastructures, program modules, or other data in a transitory modulatedsignal such as a carrier wave or other transport mechanism and includeany information delivery media. Combinations of any of the above arealso included in the scope of computer-readable media. The article ofmanufacture containing the computer code may be made and/or used byexecuting the code directly from one medium, by copying the code fromone medium to another medium, or by transmitting the code over anetwork.

This written description uses examples to disclose the embodiments,including the best mode, and also to enable any person skilled in theart to practice the embodiments, including making and using any devicesor systems and performing any incorporated methods. The patentable scopeof the disclosure is defined by the claims, and may include otherexamples that occur to those skilled in the art. Such other examples areintended to be within the scope of the claims if they have structuralelements that do not differ from the literal language of the claims, orif they include equivalent structural elements with insubstantialdifferences from the literal languages of the claims.

1-20. (canceled)
 21. A computer-based method for providing a loyaltyidentifier to a merchant using a payment network, said methodimplemented using a loyalty program (LP) computing device incommunication with a memory and a payment network server of the paymentnetwork, said method comprising: storing, in the memory, a first link toa plurality of consumer profiles, each of the consumer profilesassociated with a corresponding cardholder of a plurality of cardholdersand including a biometric reference data associated with thecorresponding cardholder; receiving, by the LP computing device from aclient device, a registration request for a first cardholder of theplurality of cardholders, the registration request including a selectionof a first of a plurality of loyalty programs and a loyalty identifierassociated with the first cardholder and the first loyalty program, eachof the plurality of loyalty programs associated with a correspondingmerchant identifier of a plurality of merchant identifiers; storing, bythe LP computing device, a second link between the loyalty identifier,the first loyalty program, and the corresponding consumer profile withinthe memory, wherein the first loyalty program includes a discountamount; receiving, by the LP computing device from the payment networkserver, a first authorization request message for a payment transactioninitiated by the first cardholder using a payment card at an originatingmerchant, the first authorization request message including a biometricscan data of the first cardholder, a first payment amount, and a firstmerchant identifier of the plurality of merchant identifiers, the firstmerchant identifier corresponding to the originating merchant; querying,by the LP computing device, the memory to identify one of the pluralityof consumer profiles having the biometric reference data matching thebiometric scan data; querying, by the LP computing device, theidentified consumer profile to determine the loyalty identifierassociated with the first loyalty program, the first loyalty programassociated with the first merchant identifier; calculating, by the LPcomputing device, a second payment amount based on the first paymentamount and the discount amount; and transmitting, by the LP computingdevice, the second payment amount and the loyalty identifier to thepayment network server.
 22. The method of claim 21 further comprising:storing, in the memory, the plurality of loyalty programs; retrieving,by the LP computing device, the first merchant identifier and thebiometric scan data from the first authorization request message; and inresponse to retrieving, automatically querying, by the LP computingdevice, the memory to identify at least one of the plurality of loyaltyprograms associated with the first merchant identifier, wherein the atleast one loyalty program includes the first loyalty program.
 23. Themethod of claim 21 further comprising: generating, by the LP computingdevice, a second authorization request message from the firstauthorization request message by replacing the first payment amount withthe second payment amount; and transmitting, by the LP computing device,the second authorization request message to the payment network server.24. The method of claim 23, wherein the payment network server isconfigured to: transmit the second authorization request message to anissuer processor computer device; receive from the issuer processorcomputer device, in response to the second authorization request messagebeing approved by the issuer processor computer device, an authorizationresponse message; format the loyalty identifier to enable inclusion ofthe loyalty identifier in the authorization response message; andtransmit the authorization response message to the originating merchantincluding the formatted loyalty identifier.
 25. The method of claim 21further comprising obtaining the biometric scan data of the firstcardholder during the payment transaction.
 26. The method of claim 21,wherein receiving the registration request from the first cardholderfurther comprises receiving, by the LP computing device, a picture of aloyalty program card associated with the first cardholder anddetermining the loyalty identifier associated with the first cardholderbased on the received picture.
 27. The method of claim 21 furthercomprising: receiving loyalty program registration information from theoriginating merchant for the first loyalty program, wherein the loyaltyprogram registration information includes the first merchant identifier;and storing, in the memory, the loyalty program registration informationfor the originating merchant including the first merchant identifier.28. A computing system for providing a loyalty identifier to a merchantusing a payment network, said computing system comprising a loyaltyprogram (LP) computing device and a payment network server, the LPcomputing device comprising one or more processors communicativelycoupled to one or more memory devices, said computing system configuredto: store, in one or more memory devices, a first link to a plurality ofconsumer profiles, each of the consumer profiles associated with acorresponding cardholder of a plurality of cardholders and including abiometric reference data associated with the corresponding cardholder;receive, from a client device, a registration request for a firstcardholder of the plurality of cardholders, the registration requestincluding a selection of a first of a plurality of loyalty programs anda loyalty identifier associated with the first cardholder and the firstloyalty program, each of the plurality of loyalty programs associatedwith a corresponding merchant identifier of a plurality of merchantidentifiers; store a second link between the loyalty identifier, thefirst loyalty program, and the corresponding consumer profile within theone or more memory devices, wherein the first loyalty program includes adiscount amount; receive, from a payment network server, a firstauthorization request message for a payment transaction initiated by thefirst cardholder using a payment card at an originating merchant, thefirst authorization request message including a biometric scan data ofthe first cardholder, a first payment amount, and a first merchantidentifier of the plurality of merchant identifiers, the first merchantidentifier corresponding to the originating merchant; query the one ormore memory devices to identify one of the plurality of consumerprofiles having the biometric reference data matching the biometric scandata; query the identified consumer profile to determine the loyaltyidentifier associated with the first loyalty program, the first loyaltyprogram associated with the first merchant identifier; calculate asecond payment amount based on the first payment amount and the discountamount; and transmit the second payment amount and the loyaltyidentifier to the payment network server.
 29. The computing system ofclaim 28 further configured to: store, in the one or more memorydevices, the plurality of loyalty programs; retrieve the first merchantidentifier and the biometric scan data from the first authorizationrequest message; and in response to retrieving, automatically query theone or more memory devices to identify at least one of the plurality ofloyalty programs associated with the first merchant identifier, whereinthe at least one loyalty program includes the first loyalty program. 30.The computing system of claim 28 further configured to: generate asecond authorization request message from the first authorizationrequest message by replacing the first payment amount with the secondpayment amount; and transmit the second authorization request message tothe payment network server.
 31. The computing system of claim 30,wherein the payment network server is configured to: transmit the secondauthorization request message to an issuer processor computer device;receive from the issuer processor computer device, in response to thesecond authorization request message being approved by the issuerprocessor computer device, an authorization response message; format theloyalty identifier to enable inclusion of the loyalty identifier in theauthorization response message; and transmit the authorization responsemessage to the originating merchant including the formatted loyaltyidentifier.
 32. The computing system of claim 28 further configured toobtain the biometric scan data of the first cardholder during thepayment transaction.
 33. The computing system of claim 28, whereinreceiving the registration request from the first cardholder furthercomprises receiving, by the LP computing device, a picture of a loyaltyprogram card associated with the first cardholder and determining theloyalty identifier associated with the first cardholder based on thereceived picture.
 34. The computing system of claim 28 furtherconfigured to: receive loyalty program registration information from theoriginating merchant for the first loyalty program, wherein the loyaltyprogram registration information includes the first merchant identifier;and store, in the one or more memory devices, the loyalty programregistration information for the originating merchant including thefirst merchant identifier.
 35. At least one non-transitorycomputer-readable storage medium having computer-executable instructionsembodied thereon, wherein when executed by an LP computing device, thecomputer-executable instructions cause the LP computing device to:store, in one or more memory devices, a first link to a plurality ofconsumer profiles, each of the consumer profiles associated with acorresponding cardholder of a plurality of cardholders and including abiometric reference data associated with the corresponding cardholder;receive, from a client device, a registration request for a firstcardholder of the plurality of cardholders, the registration requestincluding a selection of a first of a plurality of loyalty programs anda loyalty identifier associated with the first cardholder and the firstloyalty program, each of the plurality of loyalty programs associatedwith a corresponding merchant identifier of a plurality of merchantidentifiers; store a second link between the loyalty identifier, thefirst loyalty program, and the corresponding consumer profile within theone or more memory devices, wherein the first loyalty program includes adiscount amount; receive, from a payment network server, a firstauthorization request message for a payment transaction initiated by thefirst cardholder using a payment card at an originating merchant, thefirst authorization request message including a biometric scan data ofthe first cardholder, a first payment amount, and a first merchantidentifier of the plurality of merchant identifiers, the first merchantidentifier corresponding to the originating merchant; query the one ormore memory devices to identify one of the plurality of consumerprofiles having the biometric reference data matching the biometric scandata; query the identified consumer profile to determine the loyaltyidentifier associated with the first loyalty program, the first loyaltyprogram associated with the first merchant identifier; calculate asecond payment amount based on the first payment amount and the discountamount; and transmit the second payment amount and the loyaltyidentifier to the payment network server.
 36. The at least onenon-transitory computer-readable storage medium of claim 35, wherein thecomputer-executable instructions further cause the LP computing deviceto: store, in the one or more memory devices, the plurality of loyaltyprograms; retrieve the first merchant identifier and the biometric scandata from the first authorization request message; and in response toretrieving, automatically query the one or more memory devices toidentify at least one of the plurality of loyalty programs associatedwith the first merchant identifier, wherein the at least one loyaltyprogram includes the first loyalty program.
 37. The at least onenon-transitory computer-readable storage medium of claim 35, wherein thecomputer-executable instructions further cause the LP computing deviceto: generate a second authorization request message from the firstauthorization request message by replacing the first payment amount withthe second payment amount; and transmit the second authorization requestmessage.
 38. The at least one non-transitory computer-readable storagemedium of claim 35, wherein the computer-executable instructions furthercause the LP computing device to obtain the biometric scan data of thefirst cardholder during the payment transaction.
 39. The at least onenon-transitory computer-readable storage medium of claim 35, whereinreceiving the registration request from the first cardholder furthercomprises receiving, by the LP computing device, a picture of a loyaltyprogram card associated with the first cardholder and determining theloyalty identifier associated with the first cardholder based on thereceived picture.
 40. The at least one non-transitory computer-readablestorage medium of claim 35, wherein the computer-executable instructionsfurther cause the LP computing device to: receive loyalty programregistration information from the originating merchant for the firstloyalty program, wherein the loyalty program registration informationincludes the first merchant identifier; and store, in the one or morememory devices, the loyalty program registration information for theoriginating merchant including the first merchant identifier.